Preinstalled Application Management Method for Mobile Terminal and Mobile Terminal

ABSTRACT

A mobile terminal and a preinstalled application management method for a mobile terminal, where storage space of the mobile terminal includes at least one directory, and an installation package of at least one preinstalled application is stored in the at least one directory. The method includes starting the mobile terminal, scanning the at least one directory, and installing the installation package of the at least one preinstalled application in the at least one directory to generate a preinstalled application having user-level permission. Using the method and the mobile terminal, a preinstalled application can be uninstalled.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/608,282 filed on May 30, 2017, which is a continuation of U.S. patentapplication Ser. No. 14/303,907 filed on Jun. 13, 2014, now U.S. Pat.No. 9,690,561, which is a continuation of International PatentApplication No. PCT/CN2012/086435 filed on Dec. 12, 2012, which claimspriority to Chinese Patent Application No. 201110415241.9 filed on Dec.13, 2011. All of the aforementioned applications are hereby incorporatedby reference in their entireties.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not applicable.

REFERENCE TO A MICROFICHE APPENDIX

Not applicable.

TECHNICAL FIELD

Embodiments of the present disclosure relate to the field of electroniccommunications, and in particular, to a preinstalled applicationmanagement method for a mobile terminal and a mobile terminal.

BACKGROUND

A mobile terminal, such as a mobile phone, generally has applicationspreinstalled therein. In an operating system, such as an ANDROID system,a preinstalled application is stored in a system partition of a NANDFlash (generally referred to as a flash memory). When a user starts amobile phone for the first time, or restores a mobile phone to factorydefaults, the preinstalled application is installed using system-levelpermission by default, and the user cannot uninstall the preinstalledapplication as required; besides, a version of a preinstalledapplication is generally upgraded very soon, and there is a timeinterval between a manufacturer building a preinstalled application intoa mobile terminal and a user obtaining a product. As a result, whenusing the mobile terminal, the user generally receives a prompt messageindicating that the application needs to be upgraded. In this case, oncethe user updates and upgrades the application, the upgraded applicationcoexists with the preinstalled earlier-version application that cannotbe uninstalled, and therefore more space in the NAND Flash is occupiedand a waste of a space resource is caused.

SUMMARY

Embodiments of the present disclosure provide a preinstalled applicationmanagement method for a mobile terminal and a mobile terminal, which canuninstall a preinstalled application from a mobile terminal as required.

According to one aspect, an embodiment of the present disclosureprovides a preinstalled application management method for a mobileterminal, where storage space of the mobile terminal includes at leastone directory, and an installation package of at least one preinstalledapplication is stored in the at least one directory, and the methodincludes: starting the mobile terminal; scanning the at least onedirectory; and installing the installation package of the at least onepreinstalled application in the at least one directory to generate apreinstalled application having user-level permission, where the havinguser-level permission refers to that a user has permission to perform anoperation including uninstalling.

According to another aspect, an embodiment of the present disclosureprovides a mobile terminal, and the mobile terminal includes: a storingmodule configured to store at least one directory, where an installationpackage of at least one preinstalled application is stored in thedirectory; a starting module configured to start the mobile terminal; ascanning module configured to scan the at least one directory; and aninstalling module configured to install the installation package of theat least one preinstalled application in the at least one directory togenerate a preinstalled application having user-level permission, wherethe having user-level permission refers to that a user has permission toperform an operation including uninstalling.

As can be learned from the foregoing technical solutions, in theembodiments of the present disclosure, storage space of the mobileterminal includes at least one directory, and an installation package ofat least one preinstalled application is stored in the at least onedirectory; after the mobile terminal is started, the at least onedirectory is scanned, the installation package of the at least onepreinstalled application in the at least one directory is installed togenerate a preinstalled application having user-level permission.Because the installation package of the preinstalled application isinstalled using the user-level permission to generate the installationpackage with user-level permission, and because the preinstalledapplication with user-level permission is allowed to be uninstalled by auser, the preinstalled application can be uninstalled as required like athird-party application installed by the user.

BRIEF DESCRIPTION OF THE DRAWINGS

To describe the technical solutions in the embodiments of the presentdisclosure more clearly, the following briefly introduces theaccompanying drawings required for describing the embodiments. Theaccompanying drawings in the following description show merely someembodiments of the present disclosure, and a person of ordinary skill inthe art may still derive other drawings from these accompanying drawingswithout creative efforts.

FIG. 1 is a flowchart of a preinstalled application management methodfor a mobile terminal according to an embodiment of the presentdisclosure; and

FIG. 2 is a schematic structural diagram of a mobile terminal accordingto an embodiment of the present disclosure.

DETAILED DESCRIPTION

To make the objectives, technical solutions, and advantages of theembodiments of the present disclosure more clearly, the followingclearly describes the technical solutions in the embodiments of thepresent disclosure with reference to the accompanying drawings in theembodiments of the present disclosure. The described embodiments are apart rather than all of the embodiments of the present disclosure. Allother embodiments obtained by a person of ordinary skill in the artbased on the embodiments of the present disclosure without creativeefforts shall fall within the protection scope of the presentdisclosure.

Method Embodiment

Using a mobile terminal that uses an ANDROID operating system as anexample, a NAND Flash of the mobile terminal is equivalent to a harddisk of a computer and is used for storing an operating system, anapplication, and the like.

The following are typical partitions of a NAND Flash of an existingmobile terminal: modem partition including related partitions such asoriginal equipment manufacturer (oeminfo) and advanced mobile subscribersoftware (amss); boot partition storing a bootloader, and used forbooting an image during startup; system partition used for storing anoperating system and an application; user data partition (userdatapartition) used for storing file data of an application; cache partitionused for storing an instruction and cache data that are used by a systemand an application; recovery partition used for storing a small systemfor restoring to factory defaults; and miscellaneous (misc) partitionused for storing boot information for recovery.

Generally, a preinstalled application is stored in the system partition,for example, in an application directory (app directory). Afterinstallation, a generated application is an application withsystem-level permission, and a user cannot uninstall or delete theapplication.

A third-party application installed by a user is an application withuser-level permission and can be uninstalled by the user. Aninstallation package of the third-party application installed by theuser is generally in a directory in the userdata partition, for example,an app directory. When the application is installed, generated file datais also placed in the userdata partition. When the user uninstalls theinstalled third-party application, the file data generated by theapplication installed in the userdata partition is deleted, and thesystem scans the app directory in the userdata partition and deletes theinstallation package of the third-party application from the appdirectory at the same time.

As shown in FIG. 1, an embodiment of the present disclosure provides apreinstalled application management method for a mobile terminal using amobile phone that uses an ANDROID operating system as an example, but itis easy to understand that the present disclosure is not limited tothis.

Storage space of the mobile terminal includes at least one directory,and an installation package of at least one preinstalled application isstored in the at least one directory.

The at least one directory may be added to existing partitions of themobile terminal. For example, a directory may be added to each of asystem partition and a userdata partition of the mobile terminal; forexample, each of the directories is customized as a delete applicationdirectory (delapp directory), used for storing an installation packageof a preinstalled application, that is, an installation package of apreinstalled application is stored in the added system/delapp directoryand the userdata/delapp directory.

Preferably, at least one partition may be added based on the existingpartitions of the mobile terminal. For example, the at least onepartition is named cust partition, used for independently storing customdata, for example, a custom parameter, and can be considered as anextension partition of the system partition. The added at least onedirectory may be set in the added cust partition, which facilitatesmanagement of a system.

For ease of understanding, this embodiment is described using an exampleof added directories delapp being in the existing system partition anduserdata partition, that is, system/delapp and userdata/delapp, but thepresent disclosure is not limited to this.

Referring to FIG. 1, the method includes the following steps:

Step 11: Start the mobile terminal.

After the mobile terminal starts, the mobile terminal starts a PackageManager Service. After the Package Manager Service scans a systemapplication directory, the Package Manager Service adds code and scansthe customized directories: the delapp directories; that is, the PackageManager Service scans the system/delapp directory and theuserdata/delapp directory.

Step 12: Scan the at least one directory.

Step 13: Install the installation package of the at least onepreinstalled application in the at least one directory to generate apreinstalled application having user-level permission.

When the Package Manager Service scans a Package LI, the Package ManagerService installs the installation package in the delapp directory bydefault, and file data generated by the installed application is placedin the userdata partition. During installation, the Package ManagerService automatically installs the installation package in the delappdirectory using user-level permission, so as to generate thepreinstalled application having user-level permission. The user-levelpermission refers to that a user has permission to perform an operationincluding uninstalling, and the so-called preinstalled application withuser-level permission refers to a preinstalled application that allows auser to uninstall the preinstalled application.

Preferably, during installation, a custom flag, for example,PARSE_IS_REMOVABLE_PREINSTALLED, may be added for distinguishing thepreinstalled application having user-level permission from anapplication installed in system-level permission. In this way, thepreinstalled application carrying the flag is equivalent to athird-party application that has user-level permission and is installedby the user, and therefore the preinstalled application can beuninstalled.

Further, in the method provided by this embodiment of the presentdisclosure, when the user chooses to restore to factory defaults, anuninstalled preinstalled application is restored to a factory defaultstate of the preinstalled application. Therefore, the method furtherincludes: when the preinstalled application in the mobile terminal isuninstalled, uninstalling the preinstalled application to beuninstalled, and retaining an installation package of the preinstalledapplication to be uninstalled in the delapp directory. In this way, filedata of the uninstalled preinstalled application in the userdatapartition is deleted, and the application is uninstalled, but theinstallation package of the uninstalled preinstalled application stillexists in the delapp directory. When the mobile terminal is restored tofactory defaults, the preinstalled application can still be installedagain by default and restored to a factory default state of thepreinstalled application.

Preferably, the installation package of the uninstalled preinstalledapplication may be retained using an existing uninstalling mechanism ofa mobile terminal. In the existing uninstalling mechanism, whenuninstalling a third-party application having user-level permission, themobile terminal first deletes file data of the application in theuserdata partition, and scans an app directory used for storing aninstallation package of the third-party application in the userdatapartition, and then deletes the installation package of the third-partyapplication to be uninstalled that is in the app directory. Because inthis embodiment, the preinstalled program is installed using theuser-level permission, which is equivalent to a third-party applicationinstalled by a user. Therefore, the method may further include: when anapplication having user-level permission on the mobile terminal(including the preinstalled application having user-level permission andthe third-party application having user-level permission) isuninstalled, scanning the app directory in the userdata partition,determining whether an installation package of the application that hasuser-level permission and is to be uninstalled exists in the appdirectory; if the installation package of the application that hasuser-level permission and is to be uninstalled is not placed in the appdirectory, which means the application is the preinstalled applicationhaving user-level permission, uninstalling, by the mobile terminal, theapplication that has user-level permission and is to be uninstalled, andretaining the installation package of the uninstalled application havingthe user-level permission in the delapp directory. In this way, althoughthe third-party application and the preinstalled application are bothapplications with user-level permission, the installation package of thethird-party application installed by the user exists in the userdata/appdirectory, therefore not only the file data of the application isdeleted, but also the installation package of the application isdeleted; while the installation package of the preinstalled applicationis not stored in the userdata/app directory but in the system/delappdirectory and userdata/delapp directory, therefore only the file data ofthe application is deleted, and the installation package of theapplication is retained in the system/delapp directory anduserdata/delapp directory; in this way, when the mobile terminal isrestored to factory defaults, the preinstalled application can still beinstalled again by default and a factory default state of thepreinstalled application can be restored.

Preferably, the mobile terminal may be configured so that thepreinstalled application displays an uninstall button to implementuninstalling. For example, an init Uninstall Buttons interface and an onClick interface may be modified in Installed App Details, and a deletePackage LI interface may be modified in the Package Manager Service.

Further, after the generating at least one preinstalled applicationhaving user-level permission in step 13, the method further includesadding an identifier file, where the identifier file records informationfor identifying that the preinstalled application is already installedon the mobile terminal. The identifier file may be named booted, andadded to a data directory in the userdata partition, that is,userdata/data/booted.

Further, after step 11, the method further includes: determining whetherthe identifier file exists; and if the identifier file does not exist,this means that the mobile terminal is started for the first time orconsidered as being started for the first time, performing, by themobile terminal, the steps of scanning the at least one directory, andinstalling the installation package of the at least one preinstalledapplication in the at least one directory to generate a preinstalledapplication having user-level permission.

If the identifier file exists, this means that the mobile terminal isstarted at least not for the first time and the preinstalled applicationis already installed, the mobile terminal normally starts and waits foranother operation instruction. In this way, the preinstalled applicationin the delapp directory is not installed repeatedly, and the uninstalledpreinstalled application is not installed again.

It is easy to understand that when the mobile terminal is restored tofactory defaults, the booted identifier file is automatically deleted;certainly, the booted identifier file may also be deleted by the user asrequired.

Further, the preinstalled application may be uninstalled permanently asrequired. In this case, the added delapp directory cannot be set in thesystem partition, because data in the system partition cannot beoperated; in this way, after the installation package of thepreinstalled application in the system/delapp directory is installed,the generated preinstalled application having user-level permission canbe uninstalled but cannot be uninstalled permanently. The followingdescribes the permanent uninstalling of the preinstalled applicationusing the preinstalled application in the userdata/delapp directory asan example. Similar to the foregoing description, the installationpackage of the preinstalled application is installed using user-levelpermission; when the preinstalled application is uninstalled, the filedata in the userdata partition is deleted, and the installation packageof the preinstalled application in the userdata/delapp directory is alsodeleted. Alternatively, the preinstalled application may also bepermanently uninstalled using the existing uninstalling mechanism of themobile terminal, which includes: when an application having user-levelpermission (including the preinstalled application having user-levelpermission and the third-party application having user-level permission)on the mobile terminal is uninstalled, adding code so that the mobileterminal scans the app directory and the delapp directory that are inthe userdata partition, determining whether an installation package ofthe application that has user-level permission and is to be uninstalledexists in one of the app directory and the delapp directory; if yes,deleting the installation package at the same time. In this way, thepreinstalled application is considered as a third-party application andis permanently uninstalled. Once being permanently uninstalled, thepreinstalled application cannot be restored.

Preferably, when the preinstalled application is uninstalled, optionsmay be set so that the user can choose whether to uninstall (can stillbe restored to factory defaults) or permanently uninstall thepreinstalled application.

In this embodiment of the present disclosure, the preinstalledapplication is stored in an added directory, so that, on the basis ofnot changing existing settings, the system can easily identify that thepreinstalled application in the directory should be installed usinguser-level permission and the number of preinstalled applications can beconveniently increased or decreased as required, but the presentdisclosure is not limited by this as long as the terminal is led tolearn the preinstalled application installed using user-levelpermission.

In this embodiment of the present disclosure, storage space of a mobileterminal includes a delapp directory, and after a preinstalledapplication placed in the directory is decompressed, the preinstalledapplication is installed using user-level permission; in this way, thepreinstalled application is equivalent to a third-party applicationinstalled by a user and is allowed to be uninstalled by the user.Besides, an installation package of the uninstalled preinstalledapplication is still retained in the delapp; in this way, when themobile terminal is restored to factory defaults, the uninstalledpreinstalled application can be restored to a factory default state. Inaddition, when the preinstalled application is uninstalled, it may beset that the application installation package in the delapp directory isalso deleted; in this way, the preinstalled application can also bepermanently deleted.

Device Embodiment

As shown in FIG. 2, an embodiment of the present disclosure provides amobile terminal, and the mobile terminal includes the following modules:a storing module 21 configured to store at least one directory, where aninstallation package of at least one preinstalled application is storedin the directory; a starting module 22 configured to start the mobileterminal; a scanning module 23 configured to scan the at least onedirectory; and an installing module 24 configured to install theinstallation package of the at least one preinstalled application in theat least one directory to generate a preinstalled application havinguser-level permission, where the having user-level permission refers tothat a user has permission to perform an operation including anuninstalling operation.

Further, the mobile terminal further includes: a selecting module 25configured to receive an uninstalling command of a user, determine oneor more of the preinstalled applications having user-level permission asa preinstalled application to be uninstalled; and an uninstalling module26 configured to uninstall the preinstalled application to beuninstalled, and retain an installation package of the preinstalledapplication to be uninstalled.

Further, the storing module 21 includes a system partition, where the atleast one directory is not in the system partition; and the uninstallingmodule 26 is further configured to uninstall the preinstalledapplication to be uninstalled and delete the installation package of thepreinstalled application to be uninstalled stored in the at least onedirectory.

Further, the storing module further includes a user data partition,where the user data partition includes another directory, where aninstallation package of a third-party application having user-levelpermission is stored in the another directory; and the mobile terminalfurther includes a determining module 27; the selecting module 25 isfurther configured to receive an uninstalling command of a user,determine one or more of applications having user-level permission as anapplication to be uninstalled, where the applications having user-levelpermission include the preinstalled application having user-levelpermission and the third-party application having user-level permission;the scanning module 23 is further configured to scan the anotherdirectory; the determining module 27 is configured to determine whetheran installation package of the application which has user-levelpermission and is to be uninstalled exists in the another directory; andthe uninstalling module 26 is further configured to: when theinstallation package of the application which has user-level permissionand is to be uninstalled is not placed in the another directory,uninstall the application which has user-level permission and is to beuninstalled, and retain the installation package of the applicationwhich has user-level permission and is to be uninstalled.

Further, the scanning module 23 is further configured to scan theanother directory and the at least one directory; the determining module27 is further configured to determine whether the installation packageof the application which has user-level permission and is to beuninstalled is stored in the another directory or the at least onedirectory; and the uninstalling module 26 is further configured to: whenthe determining module determines that the installation package of theapplication which has user-level permission and is to be uninstalled isstored in the another directory or the at least one directory, uninstallthe application which has user-level permission and is to be uninstalledand delete the installation package of the application having user-levelpermission.

Further, the mobile terminal further includes: an identifier managementmodule 28 configured to add an identifier file after the installingmodule generates at least one preinstalled application having user-levelpermission; or configured to delete the identifier file when the mobileterminal is restored to factory defaults; or configured to delete theidentifier file when an instruction for deleting the identifier file isreceived from the user, where the identifier file records informationfor identifying that the preinstalled application is already installedon the mobile terminal.

The determining module 27 is further configured to: after the mobileterminal is started, determine whether the identifier file exists; whenthe determining module determines that the identifier file does notexist, the scanning module 23 scans the at least one directory; and theinstalling module 24 installs the installation package of the at leastone preinstalled application in the at least one directory to generatethe preinstalled application having user-level permission.

For related working principles and working processes in this embodimentof the present disclosure, reference may be made to the methodembodiment, and details are not repeated herein.

In this embodiment of the present disclosure, at least one directory isstored in the storing module 21 of the mobile terminal, and aninstallation package of at least one preinstalled application isinstalled in the directory. After the starting module 22 starts themobile terminal, the scanning module 23 scans the at least onedirectory, and the installing module 24 installs the installationpackage of the at least one preinstalled application in the at least onedirectory to generate a preinstalled application having user-levelpermission; because a preinstalled application with user-levelpermission is allowed to be uninstalled by a user, in this way, thepreinstalled application can be uninstalled as required like athird-party application installed by the user. Besides, when thepreinstalled application is uninstalled, the uninstalling module 26 mayuninstall the preinstalled application to be uninstalled, and retain aninstallation package of the preinstalled application to be uninstalledstored in the at least one directory, or delete the installation packageat the same time; in this way, the uninstalled preinstalled applicationcan still be restored to a factory default state or be permanentlydeleted.

It is easy to understand that the directory name involved in thisembodiment such as delapp is only exemplary but is not a limitation tothe present disclosure.

A person of ordinary skill in the art may understand that all or a partof the processes of the methods in the embodiments may be implemented bya computer program instructing relevant hardware. The program may bestored in a computer readable storage medium. When the program runs, theprocesses of the methods in the embodiments are performed. The foregoingstorage medium may include: a magnetic disk, an optical disc, aread-only memory (ROM), or a random access memory (RAM).

In conclusion, the foregoing embodiments are only exemplary embodimentsof the present disclosure, and are not intended to limit the presentdisclosure. Any modification, equivalent replacement, and improvementmade without departing from the spirit and principle of the presentdisclosure all fall in the protection scope of the embodiments of thepresent disclosure.

What is claimed is:
 1. A preinstalled application management method fora mobile terminal, the mobile terminal comprising storage space with afirst directory that stores an installation package of a firstpreinstalled application, the preinstalled application management methodcomprising: uninstalling, by the mobile terminal, the first preinstalledapplication, the first preinstalled application having user-levelpermission that allows uninstallation by a user, the first preinstalledapplication being installed in the mobile terminal as factory defaultsbefore the uninstalling, and the installation package being retained inthe first directory after the uninstalling; starting the mobile terminalwhen the mobile terminal is restored to factory defaults; automaticallyscanning, by the mobile terminal, the first directory; and automaticallyinstalling, by the mobile terminal, the installation package based onthe scanning to install the first preinstalled application.
 2. Thepreinstalled application management method of claim 1, wherein the firstdirectory is allocated in a system partition in the storage space of themobile terminal.
 3. The preinstalled application management method ofclaim 2, wherein the system partition stores an operating system andinstallation packages of preinstalled applications of the mobileterminal.
 4. The preinstalled application management method of claim 2,wherein data in the system partition is not accessible by the user. 5.The preinstalled application management method of claim 1, furthercomprising: receiving, by the mobile terminal, an uninstalling commandfrom the user before uninstalling the first preinstalled application;and determining, by the mobile terminal, that the first preinstalledapplication is to be uninstalled based on the uninstalling command. 6.The preinstalled application management method of claim 1, furthercomprising receiving, by the mobile terminal, an uninstalling commandfrom the user before uninstalling the first preinstalled application,the uninstalling command indicating that the first preinstalledapplication is to be uninstalled but is able to be restored when themobile terminal is restored to factory defaults.
 7. The preinstalledapplication management method of claim 1, wherein the storage spacefurther comprises a user data partition, wherein the user data partitioncomprises a second directory, wherein an installation package of athird-party application having the user-level permission is stored inthe second directory, and wherein the preinstalled applicationmanagement method further comprises: receiving, by the mobile terminal,an uninstalling command from the user; determining, by the mobileterminal, that a second application having the user-level permission isto be uninstalled based on the uninstalling command; and eitheruninstalling, by the mobile terminal, the second application anddeleting the installation package of the second application when theinstallation package of the second application is in the seconddirectory, or uninstalling, by the mobile terminal, the secondapplication and retaining the installation package of the secondapplication when the installation package of the second application isin the first directory.
 8. The preinstalled application managementmethod of claim 1, wherein the first directory is either in at least oneexisting partition in the storage space of the mobile terminal or in atleast one added partition in the storage space of the mobile terminal.9. The preinstalled application management method of claim 1, whereinthe storage space further comprises a system partition and a user datapartition, wherein the first directory is in the system partition, andwherein the installation package of the first preinstalled applicationin the first directory scanned is installed to the user data partitionto install the first preinstalled application having the user-levelpermission.
 10. A mobile terminal comprising: a non-transitory storagememory configured to store a first directory and instructions, whereinan installation package of a first preinstalled application is stored inthe first directory; and a computer processor coupled to thenon-transitory storage memory, wherein the instructions when executed bythe computer processor, cause the mobile terminal to: uninstall thefirst preinstalled application, the first preinstalled applicationhaving user-level permission that allows uninstallation by a user, thefirst preinstalled application being installed in the mobile terminal asfactory defaults before the uninstalling, and the installation packagebeing retained in the first directory after the uninstalling; start themobile terminal when the mobile terminal is restored to factorydefaults; automatically scan, in response to the starting the mobileterminal, the first directory; and automatically install theinstallation package of the first preinstalled application in the firstdirectory based on the scanning to install the first preinstalledapplication.
 11. The mobile terminal of claim 10, wherein the firstdirectory is allocated in a system partition of the mobile terminal. 12.The mobile terminal of claim 11, wherein the system partition stores anoperating system and installation packages of preinstalled applicationsof the mobile terminal.
 13. The mobile terminal of claim 11, whereindata in the system partition is not accessible by the user.
 14. Themobile terminal of claim 10, wherein the instructions when executed bythe computer processor, further cause the mobile terminal to: receive anuninstalling command from the user before uninstalling the firstpreinstalled application; and determine that the first preinstalledapplication is to be uninstalled based on the uninstalling command. 15.The mobile terminal of claim 10, wherein the instructions when executedby the computer processor, further cause the mobile terminal to receivean uninstalling command from the user before uninstalling the firstpreinstalled application, the uninstalling command indicating the firstpreinstalled application is to be uninstalled but is able to be restoredwhen the mobile terminal is restored to factory defaults.
 16. The mobileterminal of claim 10, wherein the non-transitory storage memory furthercomprises a user data partition, wherein the user data partitioncomprises a second directory, wherein an installation package of athird-party application having the user-level permission is stored inthe second directory, and wherein the instructions, when executed by thecomputer processor, further cause the mobile terminal to: receive anuninstalling command from the user; determine that a second applicationhaving the user-level permission is to be uninstalled based on theuninstalling command; and either uninstall the second application anddelete the installation package of the second application when theinstallation package of the second application is in the seconddirectory, or uninstall the second application and retain theinstallation package of the second application when the installationpackage of the second application is in the first directory.
 17. Themobile terminal of claim 16, wherein the user data partition stores filedata of applications of the mobile terminal and installation packages ofthird-party applications.
 18. The mobile terminal of claim 10, whereinthe first directory is either in at least one existing partition in thenon-transitory storage memory or in at least one added partition in thestorage space of the non-transitory storage memory.
 19. The mobileterminal of claim 10, wherein the mobile terminal is a mobile terminalthat uses an ANDROID operating system.
 20. The mobile terminal of claim10, wherein the storage space further comprises a system partition and auser data partition, wherein the first directory is in the systempartition, and wherein the installation package of the firstpreinstalled application in the first directory scanned is installed tothe user data partition to install the first preinstalled applicationhaving the user-level permission.